Uplink synchronization management in wireless networks

ABSTRACT

In at least some embodiments, a wireless networking system is provided. The wireless networking system includes a base-station and a plurality of user devices in communication with the base-station. The base-station selectively assigns each user device to one of a first group and a second group. Also, the base-station selectively assigns each user device to an uplink synchronized state and an uplink non-synchronized state. The base-station allocates a unique reduced identifier to each user device in the uplink synchronized state, but does not allocate unique reduced identifiers to user devices in the non-synchronized state.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to EP Patent Application No.06291535.0, entitled “REDUCED L1 IDENTIFIER FOR UL SYNCHRONIZED UES INE-UTRAN”, filed on Sep. 27, 2006. The above-referenced application isincorporated herein by reference.

FIELD OF THE INVENTION

The present disclosure is directed to wireless communication systems,and more particularly, but not by way of limitation, to Long TermEvolution (LTE) wireless networks.

BACKGROUND

Long Term Evolution (LTE) wireless networks also known as EnhancedUniversal Terrestrial Radio Access Network (E-UTRAN) networks are beingstandardized by Third Generation Partners Project (3GPP) working groups.For E-UTRAN networks, Orthogonal Frequency Division Multiple Access(OFDMA) is associated with downlink communications and Single-CarrierFrequency Division Multiple Access (SC-FDMA) is associated with uplinkcommunications. User equipments (UEs) of an E-UTRAN network are time andfrequency multiplexed on a shared channel such that time and frequencysynchronization are required.

The scheduler, in the base-station, has full control of the time andfrequency locations of uplink transmissions for all connected userdevices, except for UE autonomous transmissions through either thenon-synchronized random access channel or the scheduling requestchannel. To enable proper scheduling and multi-UE management, each UEshould be uniquely identified to a base-station. The 3GPP working groupshave proposed a 16-bit identifier (ID) for UE's, which representssignificant overhead costs for uplink and downlink control signaling inan E-UTRAN network because, in practical implementations, at most a fewhundred UE's (compared to 2¹⁶) will be maintained in uplinksynchronization. An uplink synchronized UE can request and have accessto uplink transmissions faster than a non-synchronized UE, which firstneeds to recover synchronization.

SUMMARY

In at least some embodiments, a wireless networking system is provided.The wireless networking system comprises a base-station and a pluralityof user devices in communication with the base-station. The base-stationselectively assigns each user device to one of a first group and asecond group. Also, the base-station selectively assigns each userdevice to an uplink synchronized state and an uplink non-synchronizedstate. The base-station allocates a unique reduced identifier to eachuser device in the uplink synchronized state, but does not allocateunique reduced identifiers to user devices in the non-synchronizedstate.

In at least some embodiments, a method is provided. The method comprisesreceiving uplink resource requests from a plurality of user devices of awireless network, each of the resource requests indicating a prioritylevel. The method further comprises assigning the user devices to one ofa first group and a second group based on the priority levels. Themethod further comprises managing uplink synchronization states of theuser devices based on timers that track an amount of time that passessince at least one of a preceding uplink transmission and a precedingreceived timing adjustment command and based on scheduling requestsreceived via a non-synchronized random access (NSRA) channel. The methodfurther comprises allocating a unique reduced identifier to each userdevice of the first group, but not to user devices of the second group.

BRIEF DESCRIPTION OF THE DRAWINGS

For a detailed description of various embodiments of the invention,reference will now be made to the accompanying drawings in which:

FIG. 1 illustrates a wireless networking system in accordance withembodiments of the disclosure;

FIG. 2 illustrates a wireless networking system in accordance withembodiments of the disclosure;

FIG. 3 illustrates a block diagram showing states of a wirelessnetworking system in accordance with embodiments of the disclosure;

FIG. 4 illustrates a time chart showing features of a wirelessnetworking system in accordance with embodiments of the disclosure; and

FIG. 5 illustrates a method in accordance with embodiments of thedisclosure.

NOTATION AND NOMENCLATURE

Certain terms are used throughout the following description and claimsto refer to particular system components. As one skilled in the art willappreciate, companies may refer to a component by different names. Thisdocument does not intend to distinguish between components that differin name but not function. In the following discussion and in the claims,the terms “including” and “comprising” are used in an open-endedfashion, and thus should be interpreted to mean “including, but notlimited to . . . ”. Also, the term “couple” or “couples” is intended tomean either an indirect, direct, optical or wireless electricalconnection. Thus, if a first device couples to a second device, thatconnection may be through a direct electrical connection, through anindirect electrical connection via other devices and connections,through an optical electrical connection, or through a wirelesselectrical connection

DETAILED DESCRIPTION

It should be understood at the outset that although an exemplaryimplementation of one embodiment of the present disclosure isillustrated below, the present system may be implemented using anynumber of techniques, whether currently known or in existence. Thepresent disclosure should in no way be limited to the exemplaryimplementations, drawings, and techniques illustrated below, includingthe exemplary design and implementation illustrated and describedherein, but may be modified within the scope of the appended claimsalong with their full scope of equivalents.

Embodiments of the disclosure relate to methods and systems for managinga wireless communication network. Although Long Term Evolution (LTE)wireless networks also known as Enhanced Universal Terrestrial RadioAccess Network (E-UTRAN) networks are mentioned herein, the methods andsystems could be used with other networks as well. As described herein,embodiments reduce control overhead costs by letting user devices(sometimes referred to as user equipments (UES)) be in two possiblestates referred to as the “uplink synchronized state” and the “uplinknon-synchronized state”. Each user device in the uplink synchronizedstate is allocated uplink resources of a base-station and is assigned,on top of its RRC/MAC 16-bit identifier (C-RNTI), a unique uplinkphysical layer identifier to temporarily ensure non-contentious uplinktransmissions via a shared communication channel or a scheduling requestchannel.

The group of user devices in the uplink non-synchronized state are notassigned any additional physical layer identifier and thus the totalnumber of bits needed for the uplink physical layer identifier in theuplink synchronized state can be reduced to improve efficiency of thecontrol signaling scheme. In at least some embodiments, each user devicein the uplink non-synchronized state cannot send uplink transmissionsuntil successfully requesting uplink resources and uplinksynchronization from the base-station. The uplink synchronized state ishereafter referred to as a “synchronized state” and the uplinknon-synchronized state is hereafter referred to as a “non-synchronizedstate”. Also, the unique uplink physical layer identifier is hereafterreferred to as a “reduced identifier” or a “unique identifier”. Thus, itshould be noted that embodiments described by these terms are notlimited to uplink synchronization or to unique uplink physical layeridentifiers.

In at least some embodiments, the assignment of user devices into thesynchronized state and the non-synchronized state is temporary. Forexample, upon a successful request for uplink resources (also referredto as uplink scheduling grant), a non-synchronized user device can bereassigned to the synchronized state and receives a reduced identifierto enable uplink transmissions and contention-free scheduling requests.On the other hand, if more than a threshold amount of time passeswithout an uplink transmission or a timing adjustment (TA) command fromthe base-station, a user device in the synchronized state can bereassigned to the non-synchronized state and the reduced identifiercorresponding to the reassigned user device is released.

FIG. 1 illustrates a wireless networking system 100 in accordance withembodiments of the disclosure. As shown in FIG. 1, the wirelessnetworking system 100 comprises a user device 102 in communication witha base-station 150. The user device 102 may represent any of a varietyof devices such as a server, a desktop computer, a laptop computer, acellular phone, a Personal Digital Assistant (PDA), a smart phone orother electronic devices. In some embodiments, the electronic device 102communicates with the base-station 150 based on a LTE or E-UTRANprotocol. Alternatively, another communication protocol now known orlater developed is used.

As shown, the electronic device 102 comprises a processor 104 coupled toa memory 106 and a transceiver 110. The memory 106 stores applications108 for execution by the processor 104. The applications 108 couldcomprise any known or future application useful for individuals ororganizations. As an example, such applications 108 could be categorizedas operating systems, device drivers, databases, multimedia tools,presentation tools, Internet browsers, emailers, Voice Over InternetProtocol (VOIP) tools, file browsers, firewalls, instant messaging,finance tools, games, word processors or other categories. Regardless ofthe exact nature of the applications 108, at least some of theapplications 108 may direct the user device 102 to transmit uplinksignals to the base-station 150 periodically or continuously via thetransceiver 110. Over time, different uplink transmissions from the userdevice 102 may be high priority (time-critical) or low priority(non-time critical). In at least some embodiments, the user device 102identifies a Quality of Service (QoS) requirement when requesting anuplink resource from the base-station 150. In some cases, the QoSrequirement may be implicitly derived by the base-station 150 from thetype of traffic supported by the user device 102. As an example, VOIPand gaming applications often involve high priority uplink transmissionswhile High Throughput (HTP)/Hypertext Transmission Protocol (HTTP)traffic involves low priority uplink transmissions.

As shown in FIG. 1, the transceiver 110 comprises uplink logic 120,which enables the user device 102 to request an uplink resource from thebase-station 150 and upon a successful request to send uplinktransmissions to the base-station 150. In FIG. 1, the uplink logic 120comprises resource request logic 122, synchronize logic 124, andtime-out logic 126. As would be understood by one of skill in the art,the components of the uplink logic 120 may involve the physical (PHY)layer and/or the Media Access Control (MAC) layer of the transceiver110.

In at least some embodiments, the resource request logic 122 detectswhen the user device 102, in absence of any valid uplink resource grant,needs to send an uplink transmission to the base-station 150 and submitsa corresponding scheduling request. As previously mentioned, the requestmay indicate a priority level or QoS requirement for the uplinktransmission. If the user device 102 is not uplink synchronized, thescheduling request is made using non-synchronized random access (NSRA)186, which is potentially contentious depending on how many other userdevices also need to use the NSRA at the same time (e.g., for schedulingrequests or uplink synchronization maintenance). Alternatively, if theuser device 102 is uplink synchronized, the resource request may besubmitted via a contention-free scheduling request channel 192 which maybe available to the user device 102.

In at least some embodiments, the scheduling request channel 192 is partof the dedicated channels 184. The dedicated channels 184 representuplink synchronized channels which are dedicated to a particular purposeand which are selectively accessible to one or more user devices.Another example of dedicated channel is the sounding reference signal(SRS). The SYS is a standalone reference signal (or pilot) whichprovides means to the base-station to perform channel qualityinformation (CQI) estimation for frequency dependent scheduling, tomaintain uplink synchronization, and to implement link adaptation andpower control for each user.

If the user device 102 previously obtained a resource allocation fromthe base-station 150 and the resource allocation has not expired, uplinktransmissions can be sent via a shared channel 182 (i.e., a channelshared with other user devices based on time and division multiplexing)in the form of a MAC Packet Data Unit (PDU) transmission. In at leastsome embodiments, the resource request logic 122 also detects when theuser device 102, with at least one valid uplink resource grant, needs toupdate its current allocated uplink resource(s) (e.g., if the userdevice 102 needs more resources because it received more data in itstransmission buffer) and submits a corresponding scheduling request.Since the user device 102 already has valid uplink grants, it is uplinksynchronized, and the resource request may be either embedded in a MACPDU sent on these valid grants on the uplink shared channel 182, orsubmitted via the scheduling request channel 192.

To use the shared channel 182 or the scheduling request channel 192, theuser device 102 receives a unique identifier from the base-station 150.In some embodiments, the unique identifier is explicitly provided by thebase-station 150 (e.g., the base-station 150 broadcasts a multi-bitunique identifier to the user device 102 for use with the shared channel182). In alternative embodiments, the unique identifier is implicitlyprovided by the base-station 150 (e.g., the base-station 150 provides aone-to-one mapping between the user device 102 and a physical uplinkresource of the scheduling request channel 192).

The synchronize logic 124 enables the user device 102 to maintain aparticular synchronization for uplink transmissions via the sharedchannel 182 or other uplink synchronized channels (e.g., the SRS or thescheduling request channel 192). In some embodiments, the synchronizelogic 124 supports time and frequency adjustments based on apredetermined protocol and/or instructions from the base-station 150.Once the user device 102 is synchronized, the synchronization can beperiodically updated based on timers and/or information exchangedbetween the user device 102 and the base-station 150. For example, ifthe user device 102 is synchronized and has at least one schedulinggrant from the base-station 150, then the synchronize manager 174 of thebase-station 150 can maintain the user device's synchronization based onongoing uplink transmissions from the user device 102 via the sharedchannel 182.

If the user device 102 is synchronized but does not have a schedulinggrant from the base-station 150, then the synchronize manager 174 of thebase-station 150 can maintain the user's synchronization based on anNSRA transmission 186. Alternatively, if the user device 102 issynchronized but does not have a scheduling grant from the base-station150, then the synchronize manager 174 of the base-station 150 canmaintain the user's synchronization based on information transmitted viaone of the dedicated channels 184 (e.g., using a SRS or an autonomoussynchronization request from the user device 102 through the schedulingrequest channel 192). By appropriately synchronizing uplinktransmissions of the user device 102, interference to and from thetransmissions of other user devices can be avoided and orthogonalmultiplexing is maintained.

As shown in FIG. 1, the base-station 150 comprises a processor 154coupled to a memory 156 and a transceiver 170. The memory 156 storesapplications 158 for execution by the processor 154. The applications158 could comprise any known or future application useful for managingwireless communications. At least some of the applications 158 maydirect the base-station to manage transmissions to or from the userdevice 102.

As shown in FIG. 1, the transceiver 160 comprises an uplink resourcemanager 170, which enables the base-station 150 to selectively allocateuplink resources to the user device 102. In FIG. 1, the uplink resourcemanager 170 comprises a state manager 172, a synchronize manager 174, ascheduling grants manager 176 and a time-out manager 178. As would beunderstood by one of skill in the art, the components of the uplinkresource manager 170 may involve the physical (PHY) layer and/or theMedia Access Control (MAC) layer of the transceiver 160.

In at least some embodiments, the state manager 172 determines whetherto assign the user device 102 to a synchronized state or to anon-synchronized state. In at least some embodiments, the user device102 can request to be assigned to the synchronized state using NSRA 186.

If the user device 102 is accepted into the synchronized state, areduced identifier is provided to the user device 102. The reducedidentifier enables the user device 102 to send uplink transmissions viathe shared channel 182 and new resource requests via the schedulingrequests channel 192. In some embodiments, the state manager 172 enablesthe reduced identifier to be explicitly provided to the user device 102(e.g., broadcasting a multi-bit unique identifier to the user device 102for use with the shared channel 182). In alternative embodiments, thestate manager 172 enables the unique identifier to be implicitlyprovided to the user device 102 (e.g., providing a one-to-one mappingbetween the user device 102 and a physical uplink resource of thebase-station 150). If the user device 102 becomes non-synchronized dueto a time-out or any other reason, the state manager 172 reassigns theuser device 102 to the non-synchronized state and releases the reducedidentifier and any associated uplink resource that was assigned to theuser device 102.

The synchronize manager 174 maintains user devices in synchronizationfor uplink transmissions via the shared channel 182 or any dedicatedchannel 184. In order to do so, the synchronize manager 174 estimatesthe timing error of the uplink transmissions of the user device 102 oneither the shared channel 182, a dedicated channel 184 (e.g., SRS) orthe NSRA 186. Then, the synchronize manager 174 sends back a timingadvance (TA) command to the user device 102, that will be executed bythe synchronize logic 124. By appropriately synchronizing uplinktransmissions of the user device 102, the synchronize manager 174 avoidsinterferences between uplink transmissions of the user device 102 anduplink transmissions of other user devices and orthogonal multiplexingis maintained.

The scheduling grants manager 176 selectively determines whensynchronized user devices will be scheduled on the shared channel 182.For example, the scheduling grants manager 176 may assign schedulinggrants in response to new resource requests from user device 102 sentthrough the scheduling request channel 192.

If more than a threshold amount of time passes during which the userdevice 102 does not send any uplink transmissions, a time-out may occur.The time-out manager 178 determines when a time-out occurs based on oneor more time-out thresholds 190. In at least some embodiments, thetime-out manager 178 implements timers or counters to track the amountof time that passes between uplink transmissions for all synchronizeduser devices. The time-out thresholds 190 may be predetermined or may bedetermined, for example, based on the number of user devices incommunication with the base-station.

In at least some embodiments, a time-out threshold causes user devicesto enter the non-synchronized state. Preferably, the entrance of userdevices to the non-synchronized state does not depend on exchangingmessages between the base-station 150 and user devices. In other words,both user devices and the base-station 150 can track the passage of timeseparately and independently determine that a user device is in anon-synchronized state. In case a user device transitions to thenon-synchronized state, any existing uplink grant of this user device isreleased.

FIG. 2 illustrates a wireless networking system 200 in accordance withembodiments of the disclosure. As shown in FIG. 2, the base-station 150discussed previously can support a plurality of user devices. Some userdevices 102A-102N have been assigned to a “time-critical group” andother user devices 102AA-102NN have been assigned to a“non-time-critical group”. The groupings can be based on information(e.g., a QoS requirement) provided with resource requests. A lack ofinformation could also determine which group (e.g., the default groupwhen insufficient information is provided could be the non-time-criticalgroup). As shown, the user devices may be reassigned from thetime-critical group to the non-time-critical group and vice versa. Forexample, a given user device in the time-critical group could bereassigned to the non-time-critical group if a time-out occurs.Meanwhile, a given user device in the non-time-critical group could bereassigned to the time-critical group if a resource request issuccessful.

As shown in FIG. 2, the uplink synchronized state involves reducedidentifiers (for use with a shared or dedicated channel), time-outperiods (e.g., scheduling grant expiration and time untilnon-synchronization), scheduling grants, and periodic synchronizationfor uplink transmissions. Meanwhile, the non-synchronized state does notinvolve synchronization or reduced identifiers. Thus, the total numberof bits needed for the reduced identifiers of the synchronized state canbe reduced to improve efficiency of the control signaling scheme. As anexample, the Cell Radio Network Temporary Identifier (C-RNTI) proposedfor LTE or E-UTRAN networks has 16-bits. Rather than use 16-bits for theunique identifier, embodiments select the number of bits used for theunique identifiers based on a maximum number of uplink synchronized userdevices to be supported by the base-station 150.

For example, if the base-station 150 supports 512 uplink synchronizeduser devices (e.g., in a 5 MHZ band), then a 9-bit identifier wouldenable each user device to be uniquely identified. Alternatively, if thebase-station 150 supports 1024 user devices (e.g., in a 10 MHZ band), a10-bit identifier would enable each user device to be uniquelyidentified. Alternatively, if the base-station 150 supports 2048 userdevices (e.g., in a 20 MHZ band), an 11-bit identifier would enable eachuser device to be uniquely identified. Any of these options (or others),would reduce the number of bits from 16-bits and improve efficiency ofthe control signal overhead. Assuming 11-bits are selected, at least30-bits would be saved for each downlink control message per TransitionTime Interval (TTI).

FIG. 3 illustrates a block diagram showing states of a wirelessnetworking system in accordance with embodiments of the disclosure. Theblock diagram represents various states of a user device of an LTE orE-UTRAN network. In FIG. 3, a Radio Resource Control (RRC) connectedstate 302 for a user device is represented. The RRC connected state 302has an uplink synchronized state 304 and an uplink non-synchronizedstate 310. The uplink synchronized state 304 indicates that the uniqueidentifier (“UE ID”) at the RRC level is C-RTNI and the uniqueidentifier at the PHY level is C-RTNI and a reduced unique identifier(i.e., a unique identifier having less than 16-bits). Also, the RadioLink Control Multiple Access Control (RLC/MAC) in the uplinksynchronized state 304 is active.

Within the uplink synchronized state 304, a “with scheduling grant”state 306 and a “without scheduling grant” state 308 is shown. The “withscheduling grant” state 306 indicates that uplink synchronization ismaintained though a shared channel (e.g., via ongoing uplinktransmissions). The “without scheduling grant” state 308 indicates thatuplink synchronization is maintained for time-critical user devices(UE's) using NSRA or dedicated channels such as a SRS or a schedulingrequest channel. The “without scheduling grant” state 308 also indicatesthat uplink synchronization is not maintained for non-time-critical userdevices (UE's). As shown, a user device in the “with scheduling grant”state 306 proceeds to the “without scheduling grant” state 308 uponexpiration of a scheduling grant. Also, a user device in the “withoutscheduling grant” state 308 proceeds to the “with scheduling grant”state 306 upon allocation of a scheduling grant (e.g., following a newscheduling request through the scheduling request channel).

FIG. 3 also indicates that a user device in the uplink synchronizedstate 304 proceeds to the uplink non-synchronized state 310 based on atime-out occurring since the last uplink transmission on the sharedchannel or since the last received timing adjustment (TA) command. Theuplink non-synchronized state 310 indicates that the unique identifier(“UE ID”) at the RRC and PHY levels is C-RTNI. The Radio Link ControlMultiple Access Control (RLC/MAC) in the uplink non-synchronized state304 is discontinuous reception (DRX). There is no maintenance of uplinksynchronization in the uplink non-synchronized state 310. Finally, auser device proceeds from the uplink non-synchronous state 310 to theuplink synchronous state 304 using a new scheduling request. The newscheduling request can only be transmitted using NSRA or a dedicatedchannel such as SRS or a resource request channel.

FIG. 4 illustrates a time chart 400 showing features of a wirelessnetworking system in accordance with embodiments of the disclosure. Thetime chart represents various features of a LTE or E-UTRAN network inaccordance with embodiments. As shown in FIG. 4, a plurality oftransmission blocks are shown on a time line. These transmission blocksare associated with a single user device. The transmission blocks on theleft of the time line are related to scheduled channels with uplinkscheduling grants. These transmission blocks occur during an active modein which uplink synchronization is achieved. As shown, a reducedidentifier (e.g., 9-11 bits) and C-RNTI are used in the active mode.

During the active mode, it may happen that the synchronized device doesnot have a scheduling grant anymore. During the time-out period, severaltransmissions blocks are shown although the order may vary. The firsttransmission block during the time-out period is a scheduling request(SR) transmission for a new uplink resource request. The secondtransmission block during the time-out period is a NSRA transmission tomaintain uplink synchronization. The third transmission block during thetime-out period is a dedicated channel transmission (e.g., SRS) tomaintain uplink synchronization.

FIG. 4 also shows a non-synchronized mode, also referred to as long DRXmode during which there is no scheduling grant for transmissions. Asshown, C-RNTI is used in the long DRX mode and the reduced uniqueidentifier is not used. One transmission block is shown in the long DRXmode. It is a NSRA transmission to recover uplink synchronization and/orto request an uplink resource.

In FIG. 4, the time-out period corresponds to the time during which auser device is maintained in uplink synchronization, although it doesnot have (nor need) any uplink resource grant. Increasing the time-outduration, increases the probability that when the user device needs anuplink resource again, the user device is still in an uplinksynchronized state where the scheduling request is more efficientcompared to the non-synchronized state. Also, increasing the time-outduration, increases the number of user devices maintained in thesynchronized state. Therefore, the time-out may be adjusted dynamicallyas a function of the number of uplink synchronized user devices.

In addition, the user devices in the uplink synchronized state areclassified into two groups: a “time-critical group” and a“non-time-critical group”. The groupings can be based on information(e.g., a QoS requirement) provided with resource requests. A lack ofinformation could also determine which group (e.g., the default groupwhen insufficient information is provided could be the non-time-criticalgroup). The time-critical group uses a longer time-out than thenon-time-critical group. The time-out of the non-time-critical group maysimply correspond to the time after which the user device is considerednon-synchronized (if its synchronization has not been maintained). Inthis case, in absence of an uplink scheduling grant, the uplinksynchronization of non-time-critical user devices is not maintained.

In at least some embodiments, user devices may be reassigned from thetime-critical group to the non-time-critical group and vice versa. Forexample, a given user device in the time-critical group could bereassigned to the non-time-critical group if its QoS requirement hasdecreased. Meanwhile, a given user device in the non-time-critical groupcould be reassigned to the time-critical group if its QoS requirementhas increased.

The timer used to determine if a time-out occurs can run from the lastuplink transmission or from the last received timing adjustment (TA). Inthe latter case, the base-station has more flexibility in controllingthe duration of the period of time during which the user device withoutuplink grant is maintained in uplink synchronization. This is becausethe base-station can maintain the TA's transmission for the desiredduration and the user device does not need to know when the TAtransmission will stop. In this case, the base-station can control alonethe difference of time during which time-critical and non-time-criticaluplink synchronized user devices without uplink scheduling grant aremaintained in the uplink synchronization state. For example, all uplinksynchronized user devices can use the same time-out threshold.

FIG. 5 illustrates a method 500 in accordance with embodiments. As shownin FIG. 5, the method 500 comprises receiving uplink resource requestsfrom a plurality of user devices of a wireless network, each resourcerequest indicating a priority level (block 502). Alternatively, some butnot all of the resource request may indicate a priority level. At block504, the user devices are assigned to one of a first group and a secondgroup based on the priority levels. In some embodiments, the prioritylevels distinguish between time-critical and non-time critical uplinktransmissions. At block 506, a unique identifier is allocated to eachuser device entering the uplink synchronized state (e.g., in the NSRAresponse). At block 508, the method 500 comprises maintaining the userdevices of the first group uplink synchronized beyond the last(preceding) uplink grant up to the expiration of a time-out and notmaintaining user devices of the second group uplink synchronized beyondthe last (preceding) uplink grant.

Dividing user devices into groups enables use of a unique identifierhaving a reduced number of bits (e.g., 9-11 instead of 16). Thus, insome embodiments, the method 500 may also comprise selecting a size ofthe first and second groups to reduce a number of bits used for theunique identifiers. Furthermore, the method 500 may comprise steps suchas providing uplink scheduling grants to user devices of the first groupin response to new resource requests based on a scheduling requestprocedure or maintaining synchronization for each user device of thefirst group without a scheduling grant via at least one of anon-synchronized random access (NSRA) communication channel, a soundingreference signal (SRS), and a scheduling request channel. Furthermore,the method 500 may comprise steps such as reassigning user devices fromthe second group to the first group based on requests received via atleast one of a non-synchronized random access (NSRA) communicationchannel and a scheduling request channel. Furthermore, the method 500may comprise steps such as broadcasting a synchronization time-outperiod to the user devices.

In at least some embodiments, a wireless networking system is provided.The wireless networking system includes a base-station and a pluralityof user devices in communication with the base-station. The base-stationselectively assigns each user device to one of a first group and asecond group. If a user device of the first group has no schedulinggrant, the base-station maintains its uplink synchronization within therange of a timer configured with respect to the base-station capacity innumber of uplink synchronized user devices. If a user device of thesecond group has no scheduling grant, the base-station does not maintainits uplink synchronization. The base-station allocates a unique reducedidentifier to each user device entering the uplink synchronizationstate, which corresponds to a physical resource of the schedulingrequest channel.

In at least some embodiments, the base-station maintains the userdevices of the first group in uplink synchronization even during periodsof time where a user device has no uplink grant, up to a certain timeout. The base-station does not maintain the uplink synchronization ofthe user devices in the second group, if they have no uplink grant. Thebase-station allocates a unique identifier to each user device enteringthe uplink synchronization state, which allows the user device to sendscheduling requests in a contention-free manner.

In at least some embodiments, a method is provided. The method comprisesreceiving uplink scheduling requests from a plurality of user devices ofa wireless network, each scheduling request indicating a priority level.The method further comprises assigning the user devices to one of afirst group and a second group based on the priority levels. The methodfurther comprises allocating a long synchronization time-out to eachuser device of the first group and allocating a shorter synchronizationtime-out to user devices of the second group.

While several embodiments have been provided in the present disclosure,it should be understood that the disclosed systems and methods may beembodied in many other specific forms without departing from the spiritor scope of the present disclosure. The present examples are to beconsidered as illustrative and not restrictive, and the intention is notto be limited to the details given herein, but may be modified withinthe scope of the appended claims along with their full scope ofequivalents. For example, the various elements or components may becombined or integrated in another system or certain features may beomitted, or not implemented.

Also, techniques, systems, subsystems and methods described andillustrated in the various embodiments as discrete or separate may becombined or integrated with other systems, modules, techniques, ormethods without departing from the scope of the present disclosure.Other items shown or discussed as directly coupled or communicating witheach other may be coupled through some interface or device, such thatthe items may no longer be considered directly coupled to each other butmay still be indirectly coupled and in communication, whetherelectrically, mechanically, or otherwise with one another. Otherexamples of changes, substitutions, and alterations are ascertainable byone skilled in the art and could be made without departing from thespirit and scope disclosed herein.

1. A wireless networking system, comprising: a base-station; a pluralityof user devices in communication with the base-station; wherein thebase-station selectively assigns each user device to one of an uplinksynchronized state and an uplink non-synchronized state; and wherein thebase-station allocates a unique reduced identifier to each user devicein the uplink synchronized state for requesting resources in acontention-free manner, but does not allocate unique reduced identifiersto user devices in the non-synchronized state.
 2. The wirelessnetworking system of claim 1 wherein a number of bits used for eachunique reduced identifier is selected based on a maximum number ofuplink synchronized user devices to be supported by the base-station. 3.The wireless networking system of claim 1 wherein a number of bits usedfor each unique reduced identifier is less than 16-bits.
 4. (canceled)5. The wireless networking system of claim 1 wherein a one-to-onemapping exists between each reduced identifier and a physical resourceof a contention-free scheduling request channel.
 6. The wirelessnetworking system of claim 1 wherein the base-station assigns userdevices requesting time-critical communications to an uplinksynchronized state and assigns all other user devices to an uplinknon-synchronized state.
 7. The wireless networking system of claim 1wherein each user device provides a Quality of Service (QoS) requirementto the base-station and wherein the base-station assigns each userdevice to one of the uplink synchronized state and the uplinknon-synchronized state based on the QoS requirement.
 8. The wirelessnetworking system of claim 1 wherein the base-station provides uplinkscheduling grants to user devices in the uplink synchronized state inresponse to new resource requests using a contention-free schedulingrequest channel.
 9. The wireless networking system of claim 1 whereinthe base-station maintains synchronization for each user device with ascheduling grant based on ongoing uplink transmissions via acommunication channel shared by user devices. 10-13. (canceled)
 14. Thewireless networking system of claim 1 wherein a given user deviceswitches from the uplink non-synchronized state to the uplinksynchronized state based on requests received via a non-synchronizedrandom access (NSRA) channel.
 15. The wireless networking system ofclaim 1 wherein the base-station broadcasts a synchronization time-outperiod to the user devices.
 16. The wireless networking system of claim1 wherein the base-station explicitly allocates a unique reducedidentifier to each user device entering the uplink synchronized state.17. The wireless networking system of claim 1 wherein the base-stationimplicitly allocates a unique reduced identifier to each user deviceentering the uplink synchronized state.
 18. A method, comprising:receiving uplink resource requests from a plurality of user devices of awireless network, each of the resource requests indicating a prioritylevel; assigning the user devices to one of an uplink synchronized stateand an uplink non-synchronized state based on the priority levels;managing uplink synchronization states of the user devices based ontimers that track an amount of time that passes since at least one of apreceding uplink transmission and a preceding received timing adjustmentcommand and based on scheduling requests received via a non-synchronizedrandom access (NSRA) channel; and allocating a unique reduced identifierto each user device of the uplink synchronized state for requestingresources in a contention-free manner, but not to user devices of theuplink non-synchronized state.
 19. The method of claim 18 furthercomprising selecting a size of the first and second states to reduce anumber of bits used for the unique reduced identifiers.
 20. The methodof claim 18 further comprising providing a one-to-one mapping betweeneach reduced identifier and a physical resource of a scheduling requestchannel.
 21. The method of claim 18 further comprising providing uplinkscheduling grants to uplink synchronized user devices in response to newresource requests received via a contention-free scheduling requestchannel.
 22. (canceled)
 23. The method of claim 18 further comprisingreassigning user devices from the non-synchronized state to thesynchronized state based on requests received via the NSRA channel. 24.The method of claim 18 further comprising broadcasting a synchronizationtime-out period to the user devices.
 25. A user equipment (UE)apparatus, comprising: a transmitter to request uplink resources in awireless network; a receiver for receiving a unique reduced identifierin response to said request when said UE has been assigned to an uplinksynchronized state by said wireless network.
 26. The wireless networkingsystem of claim 1 wherein a number of bits used for each unique reducedidentifier is selected based on a maximum number of uplink synchronizeduser devices to be supported by the base-station.
 27. The wirelessnetworking system of claim 1 wherein a number of bits used for eachunique reduced identifier is less than 16-bits.
 28. The wirelessnetworking system of claim 1 wherein a one-to-one mapping exists betweeneach reduced identifier and a physical resource of a contention-freescheduling request channel.
 29. The wireless networking system of claim1 wherein the base-station assigns user devices requesting time-criticalcommunications to an uplink synchronized state and assigns all otheruser devices to an uplink non-synchronized state.
 30. The wirelessnetworking system of claim 1 wherein each user device provides a Qualityof Service (QoS) requirement to the base-station and wherein thebase-station assigns each user device to one of the uplink synchronizedstate and the uplink non-synchronized state based on the QoSrequirement.
 31. The wireless networking system of claim 1 wherein thebase-station provides uplink scheduling grants to user devices in theuplink synchronized state in response to new resource requests using acontention-free scheduling request channel.
 32. The wireless networkingsystem of claim 1 wherein the base-station maintains synchronization foreach user device with a scheduling grant based on ongoing uplinktransmissions via a communication channel shared by user devices. 33.The wireless networking system of claim 1 wherein a given user deviceswitches from the uplink non-synchronized state to the uplinksynchronized state based on requests received via a non-synchronizedrandom access (NSRA) channel.
 34. The wireless networking system ofclaim 1 wherein the base-station broadcasts a synchronization time-outperiod to the user devices.
 35. The wireless networking system of claim1 wherein the base-station explicitly allocates a unique reducedidentifier to each user device entering the uplink synchronized state.36. The wireless networking system of claim 1 wherein the base-stationimplicitly allocates a unique reduced identifier to each user deviceentering the uplink synchronized state.
 37. The method of claim 18wherein a number of bits used for each unique reduced identifier isselected based on a maximum number of uplink synchronized user devicesto be supported.
 38. The method of claim 18 wherein a number of bitsused for each unique reduced identifier is less than 16-bits.
 39. Themethod of claim 18 wherein a one-to-one mapping exists between eachreduced identifier and a physical resource of a contention-freescheduling request channel.
 40. The method of claim 18 wherein userdevices requesting time-critical communications are assigned to anuplink synchronized state and all other user devices are assigned to anuplink non-synchronized state.
 41. The method of claim 18 wherein eachuser device provides a Quality of Service (QoS) requirement and whereineach user device is assigned to one of the uplink synchronized state andthe uplink non-synchronized state based on the QoS requirement.
 42. Themethod of claim 18 wherein uplink scheduling grants are provided to userdevices in the uplink synchronized state in response to new resourcerequests using a contention-free scheduling request channel.
 43. Themethod of claim 18 of claim 13 wherein synchronization for each userdevice with a scheduling grant is maintained based on ongoing uplinktransmissions via a communication channel shared by user devices. 44.The method of claim 18 wherein a given user device switches from theuplink non-synchronized state to the uplink synchronized state based onrequests received via a non-synchronized random access (NSRA) channel.45. The method of claim 18 wherein a synchronization time-out period isbroadcast to the user devices.
 46. The wireless networking system ofclaim 13 wherein a unique reduced identifier is specifically allocatedto each user device entering the uplink synchronized state.
 47. Thewireless networking system of claim 13 wherein a unique reducedidentifier is implicitly allocated to each user device entering theuplink synchronized state.